Method and apparatus for monitoring, assessing, and managing power source performance

ABSTRACT

An approach is provided for monitoring, assessing, and managing power source performance. Depletion of a power source of a mobile device caused by executing a plurality of activities is determined. A duration value is determined for executing each of the activities. The duration values are attributed to the depletion. Statistical data corresponding to performance of the power source is generated.

BACKGROUND INFORMATION

Consumer adoption of mobile devices, such as cellular telephones, laptopcomputers, pagers, personal digital assistants, and the like, isincreasing. These devices can be used for a diversity of purposes (oractivities) ranging from basic communications, to conducting businesstransactions, to managing entertainment media, and a host of otheractivities, e.g., asset tracking, content streaming, document editing,etc. When not plugged into an outlet, execution of one or more of theseactivities is limited to the extent with which a power source (e.g.,battery) of the mobile device can power the execution of the activities.In order to aid consumers attempting to choose one mobile device overanother, manufacturers typically provide consumers with power sourceperformance guidelines indicating, for instance, maximum amounts of time(or duration) for conducting phone calls (e.g., “talk time”), forresting in an idle state (e.g., “standby time” or “hibernation time”),for presenting content (e.g., “multimedia playback time”), and the like.This information is useful when purchasing a mobile device, however,provides little in the way of monitoring, assessing, and managing theperformance of the power supply subsequent to purchase, such as when thepower supply depletes, ages, and/or otherwise cycles.

Therefore, there is a need for an approach that can efficiently andeffectively monitor, assess, and manage power source performance.

BRIEF DESCRIPTION OF THE DRAWINGS

Various exemplary embodiments are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements and in which:

FIG. 1 is a diagram of a system configured to monitor, assess, andmanage power source performance, according to an exemplary embodiment;

FIG. 2 is a diagram of a power management platform configured tofacilitate monitoring, assessing, and managing power source performance,according to an exemplary embodiment;

FIG. 3 is a diagram of a mobile device configured to facilitatemonitoring, assessing, and managing power source performance, accordingto an exemplary embodiment;

FIG. 4 is a flowchart of a process for monitoring and assessing powersource performance, according to an exemplary embodiment;

FIG. 5 is a flowchart of a process for determining depletion of a powersource, according to an exemplary embodiment;

FIG. 6 is a flowchart of a process for determining relative performanceof a power source, according to an exemplary embodiment;

FIG. 7 is a flowchart of a process for causing a mobile device to enteran inactive state based on power source performance, according to anexemplary embodiment;

FIGS. 8 and 9 are diagrams of user interfaces configured to facilitatemonitoring, assessing, and managing power source performance, accordingto an exemplary embodiment; and

FIG. 10 is a diagram of a computer system that can be used to implementvarious exemplary embodiments.

DESCRIPTION OF THE PREFERRED EMBODIMENT

A preferred apparatus, method, and software for monitoring, assessing,and managing power source performance are described. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide a thorough understanding of thepreferred embodiments of the invention. It is apparent, however, thatthe preferred embodiments may be practiced without these specificdetails or with an equivalent arrangement. In other instances,well-known structures and devices are shown in block diagram form inorder to avoid unnecessarily obscuring the preferred embodiments of theinvention.

Although various exemplary embodiments are described with respect tomonitoring, assessing, and managing power sources associated with mobiledevices, it is contemplated that various exemplary embodiments are alsoapplicable to stationary devices. It is further contemplated thatvarious exemplary embodiments are additionally applicable toinfrastructures, facilities, and systems, whether including or embodyinga power supply.

FIG. 1 is a diagram of a system configured to monitor, assess, andmanage power source performance, according to an exemplary embodiment.For illustrative purposes, system 100 is described with respect tomonitoring, assessing, and managing performance of one or more powersources (e.g., power source 101) associated with one or more mobiledevices (e.g., mobile device 103), such as one or more cellular phones.According to certain embodiments, users at client devices (e.g.,computing device 105, voice station 107, and/or another mobile device(not shown)) may access the features and functionality of powermanagement platform (or platform) 109 over one or more networks, such asdata network 111, service provider network 113, telephony network 115,and/or wireless network 117, to remotely monitor, assess, and manageperformance of power source 101 via power source application 119 a.Alternatively (or additionally), users of mobile devices 103 may locallymonitor, assess, and manage performance of power source 101 of mobiledevice 103 via power source application 119 b. While specific referencewill be made hereto, it is contemplated that system 100 may embody manyforms and include multiple and/or alternative components and facilities.

It is observed that manufacturers of mobile devices typically providepower source statistical data or performance ratings for the performanceof a power source (e.g., battery) associated with their mobile devices.For instance, a manufacturer may specify a maximum duration for “talktime,” “standby time,” “multimedia playback time,” and the like. Thispower source performance (or capacity) information may be useful toconsumers when determining which mobile device to purchase over another,however, during the use of the mobile device, these consumers aregenerally unaware of how much actual “talk time,” “standby time,”“multimedia playback time,” etc., remains after executing a plurality ofactivities on (or by) their mobile devices. Namely, consumers may beprovided with a general indication of a remaining power source level,e.g., a percentage of remaining battery power, but such information isnot directly translatable into remaining durations for executing anumber of activities. Further, it is quite a burdensome, if notimpossible, task for a consumer to accurately determine whether thepower source associated with their mobile device is performing withinspecification, which is especially true as the power source ages.Moreover, consumers are unable to dynamically adapt the power settingsof their mobile devices. For instance, consumers are unable to controlwhen their mobile devices enter inactive states, such as, in responseto, the depletion of their power sources and/or the degradation of powersource performance over time.

Therefore, the approach of system 100, according to certain exemplaryembodiments, stems from the recognition that consumers can benefit fromthe ability to locally and/or remotely monitor, assess, and manageperformance of one or more power sources of or corresponding to theirmobile devices. Certain other exemplary embodiments stem from therecognition that enabling consumers to obtain statistical datacorresponding to power source performance in relation to one or moreactivities capable of execution on or by the mobile devices, allowsthese individuals to better understand the level at which their powersource is depleted, as well as how much actual time (or duration) isavailable for executing particular ones of these activities, e.g., phonecalls, messaging, multimedia playback, etc. Various other exemplaryembodiments stem from the recognition that enabling mobile devicesand/or users of these mobile devices to dynamically adjust (or otherwiseadapt) the power settings of these devices, creates a more satisfactoryuser experience. Namely, such a dynamic adjustment capability enablesincreased control over when a mobile device enters an inactive state,such as, in response to, the depletion of a power source of (orassociated with) the mobile device and/or the degradation of theperformance of the power source over time.

According to exemplary embodiments, users at one or more client devices103-107 may locally and/or remotely monitor, assess, and manage theperformance of one or more power sources 101 of their mobile device(s)103 via one or more of power source applications 119 a or 119 b. In thismanner, users may submit requests to (or otherwise initiate executionof) power source application 119 a and/or 119 b to obtain statisticaldata indicating the performance of power source 101. This statisticaldata may include a plurality of durations remaining for executing arespective plurality of activities on (or by) mobile device 103, mayprovide historical performance of power source 101, may compare theperformance of power source 101 with statistical data of a manufacturer,and/or may compare the performance of power source 101 with other mobiledevices (not shown) and “other” power sources (not shown).

In certain exemplary embodiments, remote monitoring, assessment, andmanagement of power source 101 may be provided via a suitable portalinterface (not illustrated), such as a voice portal or a web portal.According to certain implementations, the portal may comprise one ormore customized portlets (e.g., user interface components) arranged inone or more page layouts that provide a consistent “look and feel” foraccessing the features and functions of platform 109. In those instanceswhen the portal is implemented as (or includes) a voice portal, theportal may implement (or utilize) one or more speech synthesis and voicerecognition techniques to audibly prompt users for various informationand to reduce spoken utterances of the users and/or other signals (e.g.,dual tone multi-frequency signals) associated with the users to one ormore corresponding inputs. As such, the voice portal may provide userswith similar access to platform 109 as the web portal; however, insteadof user interactions being controlled via a “visual” interface, thevoice portal may control user interactions via an “auditory” interface.It is noted that power source application 119 a may be provided forimplementing the portal and may be deployed via platform 109; however,it is contemplated that another facility or component of system 100,such as a frontend, middleware, or backend server, may deploy powersource application 119 a and, consequently, interface with platform 109.As such, it is contemplated that power source application 119 a may beimplemented on one or more of client devices 103-107 and, thereby, beconfigured to interface with platform 109, such as is the case for powersource application 119 b. In certain embodiments, one or more of powersource applications 119 a and/or 119 b may function in conjunction withone another to achieve the features and functionalities of platform 109.

According to exemplary embodiments, the portal may include or provideusers with the ability to access, configure, manage, and store userprofile information to, for example, user profiles repository 121, aswell as the ability to monitor, assess, and manage performance of powersupply 101. As such, platform 109 may be configured to receive orretrieve power source statistical data from mobile devices 103 and,thereby, store this power supply statistical data to, for instance,power statistics repository 123. It is noted that repositories 121 and123 may be aided or supplanted by any other suitable storage location ormemory of (or accessible to) one or more of the components or facilitiesof system 100. Furthermore, and as will be described in more detail inassociation with FIG. 8, the portal may also provide users with theability to define one or more modes of communication through which usersdesire to receive results of monitoring and assessing the performance ofpower sources 101. For instance, the portal may provide users with theability to select (or otherwise provide) indications as to desired modesof delivery for the results, such as via electronic mail, shortmessaging service message, multimedia messaging service message,telephony call, facsimile, postal mail, networked applicationpresentation, and the like. As such, the portal may further enable usersto specify one or more directory addresses, email addresses, postaladdresses, uniform resource locators, identifiers, etc., foreffectuating delivery of the results to corresponding users. Whereaspower source application 119 a may provide remote monitoring,assessment, and management of power source 101, power source application119 b may provide local monitoring, assessment, and management of powersource 101 via, for instance, one or more graphical user interfaces(GUI). Exemplary GUIs are described in more detail in association withFIGS. 8 and 9.

As seen in FIG. 1, service provider network 113 enables client devices103-107 to access the features and functionalities of platform 109 viaone or more of networks 111, 115, and 117. Networks 111-117 may be anysuitable wireline and/or wireless network. For example, telephonynetwork 115 may include a circuit-switched network, such as the publicswitched telephone network (PSTN), an integrated services digitalnetwork (ISDN), a private branch exchange (PBX), or other like network.Wireless network 117 may employ various technologies including, forexample, code division multiple access (CDMA), enhanced data rates forglobal evolution (EDGE), general packet radio service (GPRS), mobile adhoc network (MANET), global system for mobile communications (GSM),Internet protocol multimedia subsystem (IMS), universal mobiletelecommunications system (UMTS), etc., as well as any other suitablewireless medium, e.g., microwave access (WiMAX), wireless fidelity(WiFi), satellite, and the like. Meanwhile, data network 111 may be anylocal area network (LAN), metropolitan area network (MAN), wide areanetwork (WAN), the Internet, or any other suitable packet-switchednetwork, such as a commercially owned, proprietary packet-switchednetwork, such as a proprietary cable or fiber-optic network.

Although depicted as separate entities, networks 111-117 may becompletely or partially contained within one another, or may embody oneor more of the aforementioned infrastructures. For instance, serviceprovider network 113 may embody circuit-switched and/or packet-switchednetworks that include facilities to provide for transport ofcircuit-switched and/or packet-based communications. It is furthercontemplated that networks 111-117 may include components and facilitiesto provide for signaling and/or bearer communications between thevarious components or facilities of system 100. In this manner, networks111-117 may embody or include portions of a signaling system 7 (SS7)network, or other suitable infrastructure to support control andsignaling functions. As such, the conjunction of networks 111-117 may beadapted to facilitate monitoring, assessing, and managing performance ofpower source 101.

According to exemplary embodiments, client devices 103-107 may includeany customer premise equipment (CPE) and/or network device capable ofsending and/or receiving information over one or more of networks111-117. For instance, voice station 107 may be any suitable plain oldtelephone service (POTS) device, facsimile machine, etc., whereas mobiledevice 103 may be any cellular phone, radiophone, satellite phone, smartphone, wireless phone, or any other suitable mobile device, such as apersonal digital assistant (PDA), pocket personal computer, tablet,customized hardware, etc. Further, computing device 105 may be anysuitable computing device, such as a VoIP phone, skinny client controlprotocol (SCCP) phone, session initiation protocol (SIP) phone, IPphone, personal computer, softphone, workstation, terminal, server, etc.Even though only a limited number of client devices 103-107 areillustrated, it is contemplated that system 100 can support a pluralityof client devices 103-107. In this manner, client devices 103-107 may beutilized to access the features and functionalities of power sourceapplication 119 a and/or 119 b to monitor, assess, and/or manage theperformance of one or more power sources of (or associated with) mobiledevice 103. As previously noted, exemplary embodiments for monitoring,assessing, and/or managing power source performance may also be appliedin monitoring, assessing, and/or managing power source performance of(or associated with) any suitable electronic device, infrastructure,facility, and/or system, whether including, being associated with, orembodying one or more power supplies. Mobile device 103 is described inmore detail in association with FIG. 3.

As previously mentioned, system 100 may also include user profilesrepository 121 for storing subscriber information, such as billinginformation, contact information, demographic information, locationinformation, mobile device configurations, subscription parameters, andthe like. Power statistics repository 123 may be provided for storingpower source performance data, such as power source statistical data ofa manufacturer corresponding to expected activity durations (e.g., “talktime,” “standby time,” multimedia playback time,” and the like),historical power source statistical data generated via one or more ofthe processes described herein, power source statistical data of “other”mobile device power sources, and the like. Even though repositories 121and 123 are depicted as extensions of service provider network 113, itis contemplated that repositories 121 and 123 may be integrated into,collocated at, or otherwise in communication with any of the variouscomponents or facilities of system 100.

In this manner, repositories 121 and 123 may be maintained by a serviceprovider of system 100 or may be maintained by any suitable third-party.It is contemplated that the physical implementation of repositories 121and 123 may take on many forms, including, for example, portions ofexisting repositories of a service provider, new repositories of aservice provider, third-party repositories, and/or shared-repositories.As such, repositories 121 and 123 may be configured for communicationover system 100 through any suitable messaging protocol, such aslightweight directory access protocol (LDAP), extensible markup language(XML), open database connectivity (ODBC), structured query language(SQL), and the like, as well as combinations thereof. In those instanceswhen repositories 121 and 123 are provided in distributed fashions,information and content available via repositories 121 and 123 may belocated utilizing any suitable querying technique, such as electronicnumber matching, distributed universal number discovery (DUNDi), uniformresource identifiers (URI), etc.

FIG. 2 is a diagram of a power management platform, according to anexemplary embodiment. Power management platform (or platform) 200 maycomprise computing hardware (such as described with respect to FIG. 10),as well as include one or more components configured to execute theprocesses described herein. In one implementation, platform 200 isimplemented by a service provider of system 100 and is configured toinclude one or more communication interfaces 201, controllers (orprocessors) 203, memories 205, power management modules 207, and userinterface modules 209. Platform 200 may also communicate with one ormore repositories, such as power statistics repository 211 and userprofiles repository 213. Users may access platform 200 (or the featuresand functionalities provided thereby) via client devices 103-107. Whilespecific reference will be made to this particular implementation, it isalso contemplated that platform 200 may embody many forms and includemultiple and/or alternative components. For example, it is contemplatedthat the components of platform 200 may be combined, located in separatestructures, or even separate locations, which, in the context of thisexample, may be components that are configured as part of or extensionsto service provider network 113.

According to one embodiment, platform 200 embodies one or moreapplication servers accessible to client devices 103-107 over one ormore of networks 111-117. Users (or subscribers) can access platform 200to create, customize, and manage one or more user profiles, as well asfor monitoring, assessing, and managing performance of power source 101associated with mobile device 103. As such, platform 200 may provide auser interface, e.g., web portal or other networked application (e.g.,voice portal), to permit users to access the features andfunctionalities of platform 200 via client devices 103-107. According tocertain embodiments, user interface module 209 may be configured forexchanging information between client devices 103-107 and a web browseror other network-based application or system, such as a voice browser orinteractive voice recognition system.

In exemplary embodiments, user interface module 209 may be configured toexecute one or more GUIs that are configured to provide users with oneor more menus of options for creating, customizing, and managing userprofiles, as well as engaging with the other features andfunctionalities of system 100, such as to remotely monitor, assess, andmanage the performance of one or more power supplies 101. In thismanner, user interface module 209 (via communication interface 201) maybe configured to receive requests to monitor the depletion of one ormore power sources 101 in relation to a plurality of activities capableof being executed on (or by) mobile device 103. In certain embodiments,this particular plurality of activities may be specified by a user (orowner) of mobile device 103. As such, user interface module 209 mayprovide requests to power management module 207 for monitoring andassessing the performance of power source(s) 101. Further, userinterface module 209 may be configured to provide one or more GUIs toremotely manage the performance of power source(s) 101.

According to exemplary embodiments, power management module 207 may beconfigured to receive and, thereby, monitor real-time power sourceperformance data (or information) generated by mobile devices 103. Powermanagement module 207 may, additionally (or alternatively), “poll”mobile devices 103 for power source data and, thereby, determine powersource performance data therefrom. In any event, data received frommobile devices 103 may be stored to power statistics repository 211 orany other suitable storage location or memory of (or accessible to)platform 200, such as memory 205. This power source data/power sourceperformance data may also be ported to user interface module 209 forpresentation to users via one or more GUIs. The operation of powermanagement module 207 is similar to that of power source application 309of FIG. 3 and, therefore, may be further understood with referencethereto, as well as with reference to FIGS. 4-9.

In order to provide selective access to the features and functionalityof platform 200, platform 200 may also include an authentication module(not illustrated) for authenticating (or authorizing) users to platform200. It is contemplated that the authentication module may operate inconcert with communication interface 201 and/or user interface module209. That is, the authentication module may verify user providedcredential information acquired via communication interface 201 and/oruser interface module 209 against corresponding credential informationstored to a user profile of, for instance, user profiles repository 213.By way of example, the credential information may include “log on”information corresponding to a user name, password, coded key, or otherunique identification parameter, such a personal identification number(PIN). In other instances, the credential information may include anyone or combination of a birth date, an account number (e.g., bank,credit card, billing code, etc.), a social security number (SSN), anaddress (e.g., work, home, internet protocol (IP), media access control(MAC), port, etc.), or telephone listing (e.g., work, home, cellular,etc.), as well as any other form of uniquely identifiable datum, e.g.,biometric code, voice print, etc. Subscribers may provide thisinformation via client devices 103-107 such as by spoken utterances,dual-tone multi-frequency (DTMF) signals, packetized transmission, etc.It is contemplated that unobtrusive security may be provided bypositively identifying and screening users based on one or more of theaforementioned credentials which may be seamlessly provided when clientdevices 103-107 communicate with platform 200, such as a unique IP orMAC address. Other unobtrusive measures can be made available via voiceprints, etc.

Additionally, platform 200 may include one or more controllers 203 foreffectuating the aforementioned features and functionalities of system100, as well as one or more memories 205 for permanent and/or temporarystorage of one or more of the aforementioned variables, parameters,information, signals, etc. In this manner, the features andfunctionalities of power source application 119 a may be implemented byplatform 200, such as, in response to, one or more memories 205including computer program code being executed by one or more ofcontrollers 203 to cause platform 200 to at least perform one or more ofthe processes described herein for monitoring, assessing, and/ormanaging power source performance.

FIG. 3 is a diagram of a mobile device configured to monitor, assess,and manage power source performance, according to an exemplaryembodiment. Mobile device 300 may comprise computing hardware (such asdescribed with respect to FIG. 10), as well as include one or morecomponents configured to execute the processes described herein formonitoring, assessing, and managing power source performance. In thisexample, mobile device 300 includes a plurality of activity applications301 a-301 n, camera 303, communications circuitry 305, one or more powersources 307, power source application 309, and user interface 311. Whilespecific reference will be made hereto, it is contemplated that mobiledevice 300 may embody many forms and include multiple and/or alternativecomponents.

According to exemplary embodiments, user interface 311 may include oneor more displays 313, keypads 315, microphones 317, and/or speakers 319.Display 313 provides a graphical user interface (GUI) that permits usersof mobile device 300 to view dialed digits, call status, menu options,and other service information, as well as monitor, assess, and manageperformance of power source(s) 307. The GUI may include icons and menus,as well as other text and symbols. Keypad 315 includes an alphanumerickeypad and may represent other input controls, such as one or morebutton controls, dials, joysticks, touch panels, etc. The user may, viaone or more components of user interface 311, conduct communications(e.g., phone calls), construct user profiles, enter commands, initializeactivity applications, input remote addresses, select options from menusystems, and/or perform any number of other like or similar mobiledevice activities. Microphone 317 coverts spoken utterances of a user(or other auditory sounds, e.g., environmental sounds) into electronicaudio signals, whereas speaker 319 converts audio signals into audiblesounds.

Communications circuitry 305 may include audio processing circuitry 321,one or more controllers 323, location module 325 (such as a GPSreceiver) coupled to antenna 327, one or more memories 329, messagingmodule 331, transceiver 333 coupled to antenna 335, and wirelesscontroller 337 coupled to antenna 339. Memory 329 may represent ahierarchy of memory, which may include both random access memory (RAM)and read-only memory (ROM). Computer program code (or instructions) andcorresponding data for operation can be stored in non-volatile memory,such as erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), and/or flash memory.Memory 329 may be implemented as one or more discrete devices, stackeddevices, or integrated with controller 323. Memory 329 may storeinformation, such as one or more user profiles, one or more user definedpolicies, one or more contact lists, personal information, sensitiveinformation, work related information, etc

According to exemplary embodiments, activity applications 301 a-301 nmay provide users with various functions for performing one or moreactivities via mobile device 300, such as browsing activities, businessactivities, calendar activities, communication activities, contactmanaging activities, content presentation activities, data editing(e.g., database, word processing, spreadsheets, etc.) activities,financial activities, gaming activities, imaging activities,location-based activities, messaging (e.g., electronic mail, IM, MMS,SMS, etc.) activities, media activities, multimedia activities, serviceactivities, storage activities, synchronization activities, taskmanaging activities, querying activities, standby state activities,powering off activities, settings activities, and the like. In thismanner, the performance of power source 307 may be monitored, assessed,and managed in relation to one or more of activity applications 301a-301 n.

Accordingly, controller 323 controls the operation of mobile device 300,such as for executing one or more activity applications 301 a-301 n and,in doing so, also monitoring, assessing, and managing performance ofpower source 307. That is, controller 323, in conjunction with one ormore instructions (or computer program code) embodying power sourceapplication 309, may cause mobile device 300 to determine depletion ofpower source 307 caused by mobile device 300 executing the one or moreactivities, to determine a duration value (e.g., accumulated executiontime) for executing each of the activities between, for instance, afirst time period and at least one second (or subsequent) time period,to attribute the durations to the depletion of power source 307, and togenerate statistical data corresponding to performance of source 307. Itis noted that an exemplary process and illustrative user interfaces formonitoring and assessing performance of power source 307 is described inmore detail in conjunction with FIGS. 4, 8, and 9.

In certain embodiments, depletion of power source 307 may be determinedbased on a difference between an initial power level of power source307, which may be determined before the one or more activities areexecuted, and a subsequent power level of power source 307, which may bedetermined subsequent to executing the one or more activities. As such,the power level may be defined in terms of any suitable datum, however,in certain exemplary embodiments, the datum may be defined in terms ofone or more duration values relating to executing the one or moreactivities. That is, the power level may be a plurality of time periodsover which particular ones of the activities may be executed beforepower source 307 would become fully (or substantially) depleted, such asX amount of remaining minutes for “talk time,” Y amount of remainingminutes for “standby time,” and Z amount of remaining minutes for“multimedia playback time.” It is noted that any number or combinationof duration values may be utilized to define the power level of powersource 307 and, in certain instances, may be particularly definedaccording to select ones of the activities, which may be selected (orspecified) by a user of mobile device 300 or, instead, may bepredetermined. According to certain other embodiments, the power levelmay be defined as a percentage value correlating a remaining powercapacity with a potential (or fully energized) capacity. In still otherembodiments, the power level may be defined in terms of remainingelectrical driving force, e.g., a remaining amount of terminal voltage.An exemplary process for determining depletion of power source 307 isdescribed in more detail in association with FIG. 5.

In this manner, the one or more instructions defining power sourceapplication 309 may, in conjunction with controller 323, cause mobiledevice 300 to attribute the duration values to the depletion of powersource 307. That is, the depletion may be defined as the result ofexecuting a certain set (or group) of one or more activities overrespective executed durations. For example, executing one or more phonecalls for a first total amount of time, executing one or more multimediaapplications for a second total amount of time, and having mobile device300 remain in an inactive standby state for a third total amount of timemay result in a first depletion of power source 300, whereas a differingcombining of activities and/or execution times may relate to variousother depletions of power source 307. As such, the particular amount ofdetermined depletion may be attributed to the determined duration valuesfor the correspondingly executed activities. These attributed depletionsmay be utilized by mobile device 103 in dynamically learning theperformance of power source 307 and, in particular instances,dynamically adapting thereto. Based on these durations values,attributed depletion amounts, historical attributed depletion amounts,power source data from a manufacturer, power source data from othermobile devices, mobile device 300 (via power source application 309 andcontroller 323) may generate statistical data corresponding toperformance of power source 309. In this manner, the statistical datamay measure performance relative to the duration values, relative to oneor more performance claims of a manufacturer, relative to historicalperformance of power source 307, and/or relative to performance of otherpower sources and/or other mobile devices.

According to exemplary embodiments, the duration values, the attributeddepletion amounts, the statistical data, the statistical data of themanufacturer, the statistical data corresponding to one or more otherpower sources and/or other mobile devices, etc., may be utilized bymobile device 300 (via power source application 309 and controller 323)to determine one or more threshold (or trigger) values for causingmobile device 300 to enter an inactive state, such as a standby state,hibernation mode, or powered off status. These threshold values may bedefined in terms of remaining duration values relating to executing oneor more of the activities, certain electrical driving forces,percentages correlating a remaining power source capacity to a potential(or fully energized) capacity, etc. As such, mobile device 300 maydynamically adjust and/or optimize how and when mobile device 300 entersor toggles between the one or more inactive states as power source 307depletes, ages, and/or cycles. It is also contemplated that, in certainexemplary embodiments, these threshold values may be user-customizableso that users may be provided with greater control over when theirmobile device becomes inactive, which, in certain instances, may be afrustrating transition when unexpected or undesired. It is noted,however, that the user may be prevented from customizing the thresholdlevels in such a manner that power source 307 may become fully (orsubstantially fully) depleted. This may be a safety feature to preventthe loss of, for instance, data (or other information) stored to avolatile memory of mobile device 300. It is also contemplated that oneor more additional threshold values may be established, so thatmonitoring the power level of power source 307 may be additionallyutilized to alert a user of mobile device 300 that the remaining powerassociated with power source 307 is approaching a level at which mobiledevice 300 will enter an inactive state, as well as (or alternatively)notify the user of one or more duration values that remain for executinga number of activities before mobile device 300 will enter the inactivestate. These notifications may be visual, audible, and/or tactile and,as such, may be presented via one or more of the components of userinterface 311 of mobile device 300. An exemplary process for causingmobile device 300 to enter an inactive state based on one or moredynamically and/or user-customized threshold values is more fullydescribed with FIG. 7.

As such, control functions may be implemented in a single controller orvia multiple controllers. Suitable controllers 323 may include, forexample, both general purpose and special purpose controllers anddigital signal processors. Controller 323 may interface with audioprocessing circuitry 321, which provides basic analog output signals tospeaker 319 and receives analog audio inputs from microphone 317. It isalso noted that mobile device 300 can be equipped with wirelesscontroller 337 to communicate with a wireless headset (not shown) orother wireless network. The headset can employ any number of standardradio technologies to communicate with wireless controller 337; forexample, the headset can be BLUETOOTH enabled. It is contemplated thatother equivalent short range radio technology and protocols can beutilized.

FIG. 4 is a flowchart of a process for monitoring and assessing powersource performance, according to an exemplary embodiment. Forillustrative purposes, the process is described with reference to mobiledevice 300 of FIG. 3. It is contemplated, however, that the process maybe executed via platform 200. Further, it is noted that the steps of theprocess may be performed in any suitable order, as well as combined orseparated in any suitable manner. At step 401, mobile device 300 via,for example, controller 323 and one or more instructions embodying powersource application 309, receives a request to monitor depletion of powersource 307 in relation to the execution of a plurality of activities on(or by) mobile device 300. For instance, mobile device 300 may present auser of mobile device 300 with a GUI interface via display 313 forinitiating the monitoring and assessment of the performance of powersource 307. In certain embodiments, the GUI interface may enable theuser to select a particular plurality of activities to monitor for theassessment of the performance of power source 307. An exemplary userinterface is described in more detail in association with FIG. 8. Instep 403, mobile device 300 via controller 323 and the one or moreinstructions determines depletion of power source 307 caused byexecuting one or more of the plurality of activities. Determination ofthe depletion of power source 307 is explained in more detail inaccordance with FIG. 5. Per step 405, a duration value (e.g., totalamount of execution time) is determined for each activity of theplurality of activities executed between initiation of power sourceapplication 309 and a subsequent time period, which may be predeterminedor established by the user via the aforementioned user interface. Theseduration values may be stored to memory 329 or any other suitablestorage location or memory of (or accessible to) mobile device 300, suchas power statistics repository 123. At step 407, the duration values areattributed to depletion of power source 307. That is, the particularamount of determined depletion is associated as being the result ofexecuting a particular plurality of activities for particular durationsof time and, as such, may be utilized to correlate the duration valuesto expected depletions. Over time, these attributed depletions may beutilized to adaptively learn the performance of power supply 307, aswell as utilized to determine the historical performance of power source307. This is described in more detail in association with FIG. 5. At anyrate, mobile device 300 may utilize one or more of the duration values,attributed depletions, historical attributed depletions, power sourcedata from a manufacturer, and/or power source data from other mobiledevices to generate (per step 409) statistical data corresponding toperformance of power source 307 in association with executing aparticular plurality of activities.

FIG. 5 is a flowchart of a process for determining depletion of a powersource, according to an exemplary embodiment. For illustrative purposes,the process is described with reference to mobile device 300 of FIG. 3.It is contemplated, however, that the process may be executed viaplatform 200. Further, it is noted that the steps of the process may beperformed in any suitable order, as well as combined or separated in anysuitable manner. At step 501, mobile device 300 via, for example,controller 323 and one or more instructions embodying power sourceapplication 309, determines an initial power level of power source 307before execution of a plurality of activities capable of being executedon (or by) mobile device 300. According to certain embodiments, thepower level may be determined relative to a completely energized powerstate of power source 307, such as a percentage of a completely, orsubstantially completely, energized power source, or may be determinedas one or more remaining durations for subsequent execution of aplurality of activities capable of implementation on (or by) mobiledevice 300. In other instances, the power level may be determined interms of a remaining amount of electrical driving force associated withpower source 307, which may be determined in any conventional manner,such as via a load tester (not shown) of mobile device 300 that may beconfigured to measure (or otherwise quantify) an “open-circuit” capacityof power source 307. It is also noted that the load tester of mobiledevice 300 may include one or more resistive elements that can bedynamically combined or separated to mimic the resistive capacities (orloads) imposed by one or more of those components of mobile device 300that are utilized in the execution of one or more of the plurality ofactivities. As such, a meter (e.g., voltmeter, ammeter, etc.) of theload tester may be utilized to measure (or otherwise quantify) a“closed-circuit” capacity of power source 307 under the mimickedresistive capacity. Based on, for example, comparisons of the“closed-circuit” capacities between a first time period and a secondtime period and an expected (or adaptively learned) full capacity,dissipated and remaining amounts of electrical driving force may bedetermined. When the process is executed via platform 200, platform 200may request or poll mobile device 300 for such information. It is notedthat this initial power level may be correlated, per step 503, with anexpected capacity (or power level) for power source 307 that, inexemplary embodiments, is defined in association with a plurality ofremaining durations for executing a plurality of activities on (or by)mobile device 300. For example, the initial power level may beconventionally measured in terms of, for example, an amount ofmilliampere-hours (mAh). Based on one or more instructions embodyingpower source application 309, controller 323 may retrieve or determine aplurality of expected durations, which may be empirically discovered viaexperimentation, “fit” to a curve, and refined based on monitoring andassessing performance of power source 307 over time.

Accordingly, in step 505, mobile device 300 may determine a subsequentpower level of power source 307 by monitoring (e.g., timing) actualduration for executing each of the plurality of activities during apredetermined interval. It is noted that each activity may be monitoredalone or as one or more groups of activities. In this manner, mobiledevice 300 may determine one or more durations for executing theplurality of activities. At step 507, mobile device 300 may determine adifference between the initial power level correlated with one or moreexpected and/or adaptively learned duration values and the one or moremonitored actual duration values. These “difference values” may beconsidered remaining duration values corresponding to one or moreamounts of time that mobile device 300 may subsequently execute one ormore of the plurality of activities. Per step 509, however, mobiledevice 300 may also correlate the “difference values” to an expectedand/or adaptively learned power level defined as an amount of, forexample, milliampere-hours, which may also be provided to the user orutilized to generate other statistical data corresponding to performanceof power source 307.

FIG. 6 is a flowchart of a process for determining relative performanceof a power source, according to an exemplary embodiment. Forillustrative purposes, the process is described with reference to mobiledevice 300 of FIG. 3. It is contemplated, however, that the process maybe executed via platform 200. Further, it is noted that the steps of theprocess may be performed in any suitable order, as well as combined orseparated in any suitable manner. It is also noted that the processassumes the existence of generated statistical data corresponding toperformance of power source 307, such as in response to the process ofFIG. 4. At step 601, mobile device 300 via, for example, controller 323and one or more instructions embodying power source application 309,retrieves statistical data of a manufacturer corresponding toperformance of power source 307 of mobile device 300 from, for example,memory 329. It is noted, however, that the statistical data of themanufacturer may be retrieved from any other suitable storage locationor memory of (or accessible to) mobile device 300, such as powerstatistics repository 211. Similarly, it is noted that platform 200 mayretrieve such information from memory 205 and power statisticsrepository 211, as well as request or poll mobile device 300 for suchinformation. In step 603, mobile device 300 determines, based on thegenerated statistical data and the retrieved statistical data of themanufacturer, relative performance of power source 307. That is, mobiledevice 300 determines the performance of power source 307 with respectto one or more specifications of the manufacturer relating to one ormore expected durations for executing activities on (or by) mobiledevice 300. The relative performance of power source 307 may be utilizedby the user of mobile device 300 for various purposes, such as, forexample, ascertaining whether power source 307 is healthy or needsreplacement, validating claims of a manufacturer, establishing one ormore threshold values (or triggers) for causing mobile device 300 toenter one or more inactive states, e.g., a standby state, hibernationmode, or powered off status, based on depletion of power source 307,etc.

FIG. 7 is a flowchart of a process for causing a mobile device to enteran inactive state based on power source performance, according to anexemplary embodiment. For illustrative purposes, the process isdescribed with reference to mobile device 300 of FIG. 3. It iscontemplated, however, that the process may be executed via platform200. In such instances, platform 200 and mobile device 300 may exchangeinformation, as well as one or more commands, instructions, or othersignals for carrying out the process. It is further noted that the stepsof the process may be performed in any suitable order, as well ascombined or separated in any suitable manner. Moreover, the processassumes the existence of generated statistical data corresponding toperformance of power source 307, such as in response to the process ofFIG. 4. At step 701, mobile device 300 via, for example, controller 323and one or more instructions embodying power source application 309,determines at least one threshold value for causing mobile device 300 toenter an inactive state. In exemplary embodiments, the at least onethreshold value may be selected so as to prevent a volatile memory ofmobile device 300 from discarding information stored thereto. That is,the at least one threshold value may be determined so that enough“standby time” or “hibernation time” can be provided via a remainingpower associated with power source 307. Although unnecessary, it isnoted that the at least one threshold value may be defined with respectto one or a plurality of reference points, such that monitoring powersource 307 need not directly monitor a remaining electrical drivingforce of power source 307. Namely, monitoring usage (or depletion) ofpower source 307 may be executed in terms of one or more remainingduration values corresponding to subsequent execution of a plurality ofactivities and/or in terms of one or more percentage values correlatinga remaining power capacity with a potential (or fully energized)capacity. Accordingly, in step 703, mobile device 300 determines (orotherwise monitors) a power level associated with power source 307. Itis noted that monitoring the power level may be performed based on adefinition of the at least one threshold value or may be converted fromone method of defining the power level to another method that can becompared (or otherwise correlated) with the at least one thresholdvalue. Per step 705, mobile device 300 may compare the determined powerlevel with the at least one threshold. At step 707, mobile device 300may determine if a monitored power level is less than or equal to atleast one threshold value. If, for example, the power level is less thanor equal to the threshold value, mobile device may generate (per step709) one or more signals to cause mobile device 300 to enter an inactivestate, such as a standby state, hibernation mode, or powered off status.If, however, the power level is greater than the at least one thresholdvalue, then mobile device 300 may continue to monitor the power level ofpower source 307. Accordingly, because the at least one threshold may bedynamically determined and implemented, mobile device 300 may optimizehow and when it enters and/or toggles between these inactive states. Itis also contemplated that one or more additional threshold values may beestablished, so that monitoring the power level of power source 307 maybe additionally utilized to alert a user of mobile device 300 that theremaining power associated with power source 307 is approaching a levelat which mobile device 300 will enter an inactive state, as well as (oralternatively) notify the user of one or more duration values thatremain for executing a number of activities before mobile device 300will enter the inactive state. These notifications may be visual,audible, and/or tactile and, as such, may be presented via one or moreof the components of user interface 311 of mobile device 300.

FIGS. 8 and 9 are diagrams of user interfaces configured to facilitatemonitoring, assessing, and managing power source performance, accordingto an exemplary embodiment. In particular, FIG. 8 is an exemplarydiagram of an illustrative user interface configured to facilitate userinitiation of monitoring and assessing performance of power source 307of mobile device 300. As shown, user interface 800 may be a GUI 800configured to be presented to a user via display 313 of mobile device300 in response to initiation of, for example, power source application309. It is noted, however, that GUI 800 may be provided to remote usersvia user interface module 209. Hence, GUI 800 includes a plurality ofregions (e.g., regions 801, 803, 805, and 807) for configuring mobiledevice 300 for monitoring performance of power source 307 in relation toexecution of a plurality of activities on (or by) mobile device 300. Inthis manner, region 801 provides users with a plurality of selectableactivities, such as “ACTIVITY ‘1’”-“ACTIVITY ‘N,’” for monitoring andassessing performance of power source 307. According to certainembodiments, selection of activities in region 801 may be implementedvia one or more interactive GUI elements, such as one or more radiobuttons, e.g., radio button 809.

Region 803 enables users to select, e.g., via interactive GUI elements811 or 813, whether or not a user desires to receive performance ofpower source 307 in terms of remaining durations (e.g., amounts ofremaining time) for subsequent execution of the plurality of activitiesspecified in, for example, region 801. It is noted that if no activitiesare selected in region 801, power source application 309 may beconfigured to monitor and assess performance of power source 307 inrelation to a default plurality of activities or in relation to allactivities executed on (or by) mobile device 300. In this manner, region805 further enables users to be presented with one or more relativepower source performance assessments, such as to verify a specificationof a manufacturer of power source 307 and/or mobile device 300, todetermine “current” performance in relation to historical performance ofpower source 307, and to determine performance of power source 307 inrelation to one or more “other” mobile devices or “other” power sources.As before, one or more interactive GUI elements (e.g., interactive GUIelement 815) may be provided for users to select desired relativeperformance assessments. Accordingly, region (or start button) 807enables users to initiate monitoring and assessment of the performanceof power source 307 based on the selections of regions 801-803. Eventhough not illustrated, GUI 800 may also provide users with the abilityto define one or more modes of communication through which the userdesires to receive the results of the monitoring and assessing of theperformance of power source 307. For instance, GUI 800 may provideanother region for the user to select delivery of the results via one ormore of electronic mail, short messaging service message, multimediamessaging service message, telephony call, facsimile, postal mail,networked application presentation, and the like. As such, this otherregion may further provide one or more input fields for specifying oneor more directory addresses, electronic mail addresses, postaladdresses, uniform resource locators, identifiers, etc., for deliveringthe results to the user. Accordingly, mobile device 300 and/or platform200 may be configured to transmit (or otherwise deliver) the results ofthe monitoring and assessing of the performance of power source 307 tothe user-specified directory addresses, email addresses, postaladdresses, uniform resource locators, identifier, and/or the like.

FIG. 9 is an exemplary diagram of an illustrative user interfaceconfigured to provide statistical data corresponding to performance of apower source, as well as provide one or more interactive features formanaging performance of the power source. In this example, it is assumedthat user interface 900 is a GUI 900 and is presented to a user viadisplay 313 of mobile device 300 in response to a request to monitordepletion of power source 307 in relation to a plurality of activities,e.g., “ACTIVITY ‘1’”-“ACTIVITY ‘N.’” Hence, GUI 900 includes a pluralityof regions (e.g., regions 901, 903, and 905) for displaying statisticaldata and/or one or more power source management settings of mobiledevice 300. For instance, region 901 may provide a plurality ofremaining activity durations 907 indicating respective amounts of timeeach activity may be executed before power source 307 is fully (orsubstantially fully) depleted. In certain embodiments, a pie chart (orother graphical depiction) 909 may be provided to pictorially illustrateremaining activity durations 907. Region 903 may provide a plurality ofrelative performances 911 indicating performance of power supply 307 inrelation to, for example, statistical data of a manufacturer. Namely,relative performances 911 enable a user to assess whether power supply307 is performing within one or more asserted performance claims of themanufacturer. For example, power supply 307 is able to provide aboveaverage performance for “ACTIVITY ‘N,’” whereas the respectiveperformances of “ACTIVITY ‘1’” and “ACTIVITY ‘2’” are about average.Region 905 provides a plurality of inactive state settings (orthresholds) 913 for causing mobile device 300 to enter an inactivestate, such as a standby state, hibernation mode, or a powered offstatus. In this manner, if one or more of the remaining activitydurations 907 are, for instance, respectively less than or equal to oneor more of the thresholds 913, then mobile device 300 may enter aparticular one of the inactive states. According to exemplaryembodiments, threshold levels 913 may be user adjustable. As such, oneor more interactive GUI components 915 may be provided to enable usersto adjust thresholds 915 up or down, i.e., by adding or removingremaining activity duration.

The processes described herein for monitoring, assessing, and managingpower source performance may be implemented via software, hardware(e.g., general processor, Digital Signal Processing (DSP) chip, anApplication Specific Integrated Circuit (ASIC), Field Programmable GateArrays (FPGAs), etc.), firmware or a combination thereof. Such exemplaryhardware for performing the described functions is detailed below.

FIG. 10 illustrates computing hardware (e.g., computer system) 1000 uponwhich exemplary embodiments can be implemented. The computer system 1000includes a bus 1001 or other communication mechanism for communicatinginformation and a processor 1003 coupled to the bus 1001 for processinginformation. The computer system 1000 also includes main memory 1005,such as a random access memory (RAM) or other dynamic storage device,coupled to the bus 1001 for storing information and instructions to beexecuted by the processor 1003. Main memory 1005 can also be used forstoring temporary variables or other intermediate information duringexecution of instructions by the processor 1003. The computer system1000 may further include a read only memory (ROM) 1007 or other staticstorage device coupled to the bus 1001 for storing static informationand instructions for the processor 1003. A storage device 1009, such asa magnetic disk or optical disk, is coupled to the bus 1001 forpersistently storing information and instructions.

The computer system 1000 may be coupled via the bus 1001 to a display1011, such as a cathode ray tube (CRT), liquid crystal display, activematrix display, or plasma display, for displaying information to acomputer user. An input device 1013, such as a keyboard includingalphanumeric and other keys, is coupled to the bus 1001 forcommunicating information and command selections to the processor 1003.Another type of user input device is a cursor control 1015, such as amouse, a trackball, or cursor direction keys, for communicatingdirection information and command selections to the processor 1003 andfor controlling cursor movement on the display 1011.

According to an exemplary embodiment, the processes described herein areperformed by the computer system 1000, in response to the processor 1003executing an arrangement of instructions contained in main memory 1005.Such instructions can be read into main memory 1005 from anothercomputer-readable medium, such as the storage device 1009. Execution ofthe arrangement of instructions contained in main memory 1005 causes theprocessor 1003 to perform the process steps described herein. One ormore processors in a multi-processing arrangement may also be employedto execute the instructions contained in main memory 1005. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions to implement exemplaryembodiments. Thus, exemplary embodiments are not limited to any specificcombination of hardware circuitry and software.

The computer system 1000 also includes a communication interface 1017coupled to bus 1001. The communication interface 1017 provides a two-waydata communication coupling to a network link 1019 connected to a localnetwork 1021. For example, the communication interface 1017 may be adigital subscriber line (DSL) card or modem, an integrated servicesdigital network (ISDN) card, a cable modem, a telephone modem, or anyother communication interface to provide a data communication connectionto a corresponding type of communication line. As another example,communication interface 1017 may be a local area network (LAN) card(e.g. for Ethernet™ or an Asynchronous Transfer Model (ATM) network) toprovide a data communication connection to a compatible LAN. Wirelesslinks can also be implemented. In any such implementation, communicationinterface 1017 sends and receives electrical, electromagnetic, oroptical signals that carry digital data streams representing varioustypes of information. Further, the communication interface 1017 caninclude peripheral interface devices, such as a Universal Serial Bus(USB) interface, a PCMCIA (Personal Computer Memory Card InternationalAssociation) interface, etc. Although a single communication interface1017 is depicted in FIG. 10, multiple communication interfaces can alsobe employed.

The network link 1019 typically provides data communication through oneor more networks to other data devices. For example, the network link1019 may provide a connection through local network 1021 to a hostcomputer 1023, which has connectivity to a network 1025 (e.g. a widearea network (WAN) or the global packet data communication network nowcommonly referred to as the “Internet”) or to data equipment operated bya service provider. The local network 1021 and the network 1025 both useelectrical, electromagnetic, or optical signals to convey informationand instructions. The signals through the various networks and thesignals on the network link 1019 and through the communication interface1017, which communicate digital data with the computer system 1000, areexemplary forms of carrier waves bearing the information andinstructions.

The computer system 1000 can send messages and receive data, includingprogram code, through the network(s), the network link 1019, and thecommunication interface 1017. In the Internet example, a server (notshown) might transmit requested code belonging to an application programfor implementing an exemplary embodiment through the network 1025, thelocal network 1021 and the communication interface 1017. The processor1003 may execute the transmitted code while being received and/or storethe code in the storage device 1009, or other non-volatile storage forlater execution. In this manner, the computer system 1000 may obtainapplication code in the form of a carrier wave.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing instructions to the processor 1003 forexecution. Such a medium may take many forms, including but not limitedto non-volatile media, volatile media, and transmission media.Non-volatile media include, for example, optical or magnetic disks, suchas the storage device 1009. Volatile media include dynamic memory, suchas main memory 1005. Transmission media include coaxial cables, copperwire and fiber optics, including the wires that comprise the bus 1001.Transmission media can also take the form of acoustic, optical, orelectromagnetic waves, such as those generated during radio frequency(RF) and infrared (IR) data communications. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM,CDRW, DVD, any other optical medium, punch cards, paper tape, opticalmark sheets, any other physical medium with patterns of holes or otheroptically recognizable indicia, a RAM, a PROM, and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave, or any other mediumfrom which a computer can read.

Various forms of computer-readable media may be involved in providinginstructions to a processor for execution. For example, the instructionsfor carrying out at least part of the exemplary embodiments mayinitially be borne on a magnetic disk of a remote computer. In such ascenario, the remote computer loads the instructions into main memoryand sends the instructions over a telephone line using a modem. A modemof a local computer system receives the data on the telephone line anduses an infrared transmitter to convert the data to an infrared signaland transmit the infrared signal to a portable computing device, such asa personal digital assistant (PDA) or a laptop. An infrared detector onthe portable computing device receives the information and instructionsborne by the infrared signal and places the data on a bus. The busconveys the data to main memory, from which a processor retrieves andexecutes the instructions. The instructions received by main memory canoptionally be stored on storage device either before or after executionby processor.

While certain exemplary embodiments and implementations have beendescribed herein, other embodiments and modifications will be apparentfrom this description. Accordingly, the invention is not limited to suchembodiments, but rather to the broader scope of the presented claims andvarious obvious modifications and equivalent arrangements.

1. A method comprising: determining depletion of a power source of amobile device caused by the mobile device executing a plurality ofactivities; determining a duration value for executing each of theactivities; attributing the duration values to the depletion; andgenerating statistical data corresponding to performance of the powersource.
 2. A method according to claim 1, further comprising:determining an initial power level of the power source before theplurality of activities are executed; and determining a subsequent powerlevel of the power source, wherein determining the depletion of thepower source is based on a difference between the initial power leveland the subsequent power level.
 3. A method according to claim 1,further comprising: retrieving statistical data of a manufacturercorresponding to performance of the power source; and determining, basedon the generated statistical data and the statistical data of themanufacturer, relative performance of the power source.
 4. A methodaccording to claim 1, further comprising: determining, based on thestatistical data, at least one threshold value for causing the mobiledevice to enter an inactive state.
 5. A method according to claim 4,wherein the at least one threshold value is further determined based onhistorical generated statistical data.
 6. A method according to claim 4,wherein the inactive state is a standby state, hibernation mode, or apowered off status of the mobile device.
 7. A method according to claim4, further comprising: determining a power level of the power source;comparing the power level with the at least one threshold value; andgenerating, if the power level is less than or equal to the thresholdvalue, a signal to cause the mobile device to enter the inactive state.8. A method according to claim 7, wherein the power level and the atleast one threshold value are defined as remaining durations forsubsequent execution of the plurality of activities.
 9. A methodaccording to claim 1, wherein the statistical data relates to arespective plurality of remaining durations for subsequent execution ofthe plurality of activities.
 10. A method according to claim 1, furthercomprising: receiving a request to monitor the depletion in relation toa particular plurality of activities, wherein the particular pluralityof activities are specified by a user of the mobile device.
 11. A methodaccording to claim 1, wherein the activities include one or more of astandby activity, a communication activity, and a content presentationactivity.
 12. An apparatus comprising: at least one power source; atleast one processor; and at least one memory including computer programcode, the at least one memory and the computer program code beingconfigured to, with the at least one processor, cause the apparatus atleast to: determine depletion of the at least one power source caused bythe apparatus executing a plurality of activities; determine a durationvalue for executing each of the activities; attribute the durationvalues to the depletion; and generate statistical data corresponding toperformance of the at least one power source.
 13. An apparatus accordingto claim 12, wherein the at least one memory and the computer programcode are further configured to, with the at least one processor, causethe apparatus at least to: determine an initial power level of the atleast one power source before the plurality of activities are executed;and determine a subsequent power level of the at least one power source,wherein the depletion of the power source is determined based on adifference between the initial power level and the subsequent powerlevel.
 14. An apparatus according to claim 12, wherein the at least onememory and the computer program code are further configured to, with theat least one processor, cause the apparatus at least to: retrievestatistical data of a manufacturer corresponding to performance of theat least one power source; and determine, based on the generatedstatistical data and the statistical data of the manufacturer, relativeperformance of the power source.
 15. An apparatus according to claim 12,wherein the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus at least to: determine, based on the statistical data, atleast one threshold value for causing the apparatus to enter an inactivestate.
 16. An apparatus according to claim 15, wherein the at least onethreshold value is further determined based on historical generatedstatistical data.
 17. An apparatus according to claim 15, wherein theinactive state is a standby state, a hibernation mode, or a power offstatus of the apparatus.
 18. An apparatus according to claim 15, whereinthe at least one memory and the computer program code are furtherconfigured to, with the at least one processor, cause the apparatus atleast to: determine a power level of the at least one power source;compare the power level with the at least one threshold value; andgenerate, if the power level is less than or equal to the thresholdvalue, a signal to cause the apparatus to enter the inactive state. 19.An apparatus according to claim 18, wherein the power level and the atleast one threshold value are defined as remaining durations forsubsequent execution of the plurality of activities.
 20. An apparatusaccording to claim 12, wherein the statistical data relates to arespective plurality of remaining durations for subsequent execution ofthe plurality of activities.
 21. An apparatus according to claim 12,wherein the at least one memory and the computer program code arefurther configured to, with the at least one processor, cause theapparatus at least to: receive a request to monitor the depletion inrelation to a particular plurality of activities, wherein the particularplurality of activities are specified by a user of the apparatus.
 22. Anapparatus according to claim 12, wherein the activities include one ormore of a standby activity, a communication activity, and a contentpresentation activity.